Method of transmitting and receiving downlink data channel and apparatus therefor

ABSTRACT

A method of receiving a Physical Downlink Shared Channel (PDSCH) includes: receiving, in a first bandwidth part (BWP), a downlink control information (DCI) including (i) first information that indicates switching an active BWP from the first BWP to a second BWP, and (ii) second information related to scheduling at least one transport block (TB) for the PDSCH; and receiving, in the second BWP, the PDSCH based on the first information and the second information. Based on a number of TBs in a first group of TBs that can be scheduled through the second information being equal to one, and based on a number of TBs in a second group of TBs that can be scheduled for the second BWP being equal to two: among the second information related to scheduling the at least one TB, information related to a second TB among the second group of TBs is disabled.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/376,510, filed on Apr. 5, 2019, now allowed, which claims the benefitof U.S. Provisional Application No. 62/653,532, filed on Apr. 5, 2018,and U.S. Provisional Application No. 62/670,024, filed on May 11, 2018.The disclosures of the prior applications are incorporated by referencein their entirety.

TECHNICAL FIELD

The present disclosure generally relates to a wireless communicationsystem.

BACKGROUND

A new generation of wireless broadband communications, known as the5^(th)-generation (5G), is being designed for telecommunication devicesthat demand increasing amounts of communication traffic. In this nextgeneration 5G system, sometimes referred to as NewRAT, communicationscenarios include Enhanced Mobile BroadBand (eMBB)/Ultra-reliability andlow latency communication (URLLC)/Massive Machine-Type Communications(mMTC).

In particular, eMBB is a next generation mobile communication scenariohaving characteristics such as High Spectrum Efficiency, High UserExperienced Data Rate, and High Peak Data Rate. URLLC is a nextgeneration mobile communication scenario having characteristics such asUltra Reliable, Ultra Low Latency, such as for vehicle-to-everything(V2X) communications, Emergency Service, and Remote Control. mMTC is anext generation mobile communication scenario with low cost, low energy,short packet, and massive connectivity, such as for Internet of Things(IoT).

SUMMARY

Implementations disclosed herein relate to transmitting and receivingdownlink data channels.

One general aspect of the present disclosure includes a method ofreceiving a physical downlink shared channel (PDSCH) by a user equipment(UE) in a wireless communication system, the method including:receiving, in a first bandwidth part (BWP), a downlink controlinformation (DCI) that includes (i) first information that indicatesswitching an active BWP from the first BWP to a second BWP, and (ii)second information related to scheduling at least one transport block(TB) for the PDSCH. The method also includes receiving, in the secondBWP, the PDSCH based on the first information and the secondinformation, where based on a number of TBs in a first group of TBs thatcan be scheduled through the second information being equal to one, andbased on a number of TBs in a second group of TBs that can be scheduledfor the second BWP being equal to two: among the second informationrelated to scheduling the at least one TB, information related to asecond TB among the second group of TBs is disabled. Other embodimentsof this aspect include corresponding computer systems, apparatus, andcomputer programs recorded on one or more computer storage devices, eachconfigured to perform the actions of the methods.

Implementations may include one or more of the following features. Themethod where the second information related to scheduling the at leastone TB includes: a set of bits related to a modulation and coding scheme(MCS), a new data indicator (NDI), and a redundancy version (RV). Themethod where the information related to the second TB is zero-padded.The method where the information related to the second TB is ignored.The method where transmission configuration information (TCI) for thesecond BWP is same as TCI information related to the DCI. The methodwhere the TCI information related to the DCI includes: TCI informationfor a control resource set (CORESET) that is related to the DCI.Implementations of the described techniques may include hardware, amethod or process, or computer software on a computer-accessible medium.

Another general aspect includes an apparatus configured to receive aphysical downlink shared channel (PDSCH) in a wireless communicationsystem, the apparatus including: at least one processor; and at leastone memory operably connectable to the at least one processor andstoring instructions that, when executed by the at least one processor,perform operations including: receiving, in a first bandwidth part(BWP), a downlink control information (DCI) that includes (i) firstinformation that indicates switching an active BWP from the first BWP toa second BWP, and (ii) second information related to scheduling at leastone transport block (TB) for the PDSCH. The operations also includereceiving, in the second BWP, the PDSCH based on the first informationand the second information, where based on a number of TBs in a firstgroup of TBs that can be scheduled through the second information beingequal to one, and based on a number of TBs in a second group of TBs thatcan be scheduled for the second BWP being equal to two: among the secondinformation related to scheduling the at least one TB, informationrelated to a second TB among the second group of TBs is disabled. Otherembodiments of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

Implementations may include one or more of the following features. Theapparatus where the second information related to scheduling the atleast one TB includes: a set of bits related to a modulation and codingscheme (MCS), a new data indicator (NDI), and a redundancy version (RV).The apparatus where the information related to the second TB iszero-padded. The apparatus where the information related to the secondTB is ignored. The apparatus where transmission configurationinformation (TCI) for the second BWP is same as TCI information relatedto the DCI. The apparatus where the TCI information related to the DCIincludes: TCI information for a control resource set (CORESET) that isrelated to the DCI. Implementations of the described techniques mayinclude hardware, a method or process, or computer software on acomputer-accessible medium.

Another general aspect includes a user equipment (UE) configured toreceive a physical downlink shared channel (PDSCH) in a wirelesscommunication system, the UE including: a transceiver. The userequipment also includes at least one processor; and at least one memoryoperably connectable to the at least one processor and storinginstructions that, when executed by the at least one processor, performoperations including: receiving, in a first bandwidth part (BWP), adownlink control information (DCI) that includes (i) first informationthat indicates switching an active BWP from the first BWP to a secondBWP, and (ii) second information related to scheduling at least onetransport block (TB) for the PDSCH. The operations also includesreceiving, in the second BWP, the PDSCH based on the first informationand the second information, where based on a number of TBs in a firstgroup of TBs that can be scheduled through the second information beingequal to one, and based on a number of TBs in a second group of TBs thatcan be scheduled for the second BWP being equal to two: among the secondinformation related to scheduling the at least one TB, informationrelated to a second TB among the second group of TBs is disabled. Otherembodiments of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

Another general aspect includes a method of transmitting a physicaldownlink shared channel (PDSCH) in a wireless communication system, themethod including: transmitting, in a first bandwidth part (BWP), adownlink control information (DCI) that includes (i) first informationthat indicates switching an active BWP from the first BWP to a secondBWP, and (ii) second information related to scheduling at least onetransport block (TB) for the PDSCH. The method also includestransmitting, in the second BWP, the PDSCH based on the firstinformation and the second information, where based on a number of TBsin a first group of TBs that can be scheduled through the secondinformation being equal to one, and based on a number of TBs in a secondgroup of TBs that can be scheduled for the second BWP being equal totwo: among the second information related to scheduling the at least oneTB, information related to a second TB among the second group of TBs isdisabled. Other embodiments of this aspect include correspondingcomputer systems, apparatus, and computer programs recorded on one ormore computer storage devices, each configured to perform the actions ofthe methods.

Another general aspect includes a base station (BS) configured totransmit a physical downlink shared channel (PDSCH) in a wirelesscommunication system, the BS including: a transceiver. The base stationalso includes at least one processor; and at least one memory operablyconnectable to the at least one processor and storing instructions that,when executed by the at least one processor, perform operationsincluding: transmitting, in a first bandwidth part (BWP), a downlinkcontrol information (DCI) that includes (i) first information thatindicates switching an active BWP from the first BWP to a second BWP,and (ii) second information related to scheduling at least one transportblock (TB) for the PDSCH. The operations also include transmitting, inthe second BWP, the PDSCH based on the first information and the secondinformation, where based on a number of TBs in a first group of TBs thatcan be scheduled through the second information being equal to one, andbased on a number of TBs in a second group of TBs that can be scheduledfor the second BWP being equal to two: among the second informationrelated to scheduling the at least one TB, information related to asecond TB among the second group of TBs is disabled. Other embodimentsof this aspect include corresponding computer systems, apparatus, andcomputer programs recorded on one or more computer storage devices, eachconfigured to perform the actions of the methods.

All or part of the features described throughout this application can beimplemented as a computer program product including instructions thatare stored on one or more non-transitory machine-readable storage media,and that are executable on one or more processing devices. All or partof the features described throughout this application can be implementedas an apparatus, method, or electronic system that can include one ormore processing devices and memory to store executable instructions toimplement the stated functions.

The details of one or more implementations of the subject matter of thisdisclosure are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing an example of a control plane and a userplane structure of a wireless interface protocol between a terminal andan E-UTRAN based on the 3GPP radio access network standard;

FIG. 2 is a diagram showing an example of a physical channel used in a3GPP system and a general signal transmission method using the same;

FIGS. 3 to 5 are diagrams showing examples of structures of radio framesand slots used in a wireless communication system;

FIG. 6 is a diagram showing an example a hybrid beamforming structure interms of a transceiver unit (TXRU) and a physical antenna;

FIG. 7 is a diagram showing an example of a beam sweeping operation fora synchronization signal and system information in a downlinktransmission process;

FIG. 8 is a diagram showing an example of a cell of a new radio accesstechnology (NR) system;

FIG. 9 is a diagram showing an example of HARQ-ACK timing in the NRsystem;

FIGS. 10 to 11 are diagrams showing examples of HARQ-ACK transmission inunits of a code block group (CBG) in the NR system;

FIGS. 12 to 14 are diagrams showing examples of HARQ-ACK transmission inCarrier Aggregation (CA);

FIGS. 15 to 17 are diagrams showing examples of operations of aterminal, a BS, and a network for transmitting and receiving HARQ-ACKaccording to implementations of the present disclosure;

FIG. 18 is a diagram showing an example in which the DCI schedules thePDSCH according to implementations of the present disclosure;

FIGS. 19 to 21 are diagrams showing examples of operations of aterminal, a base station and a network for transmitting and receiving aPDSCH according to implementations of the present disclosure; and

FIG. 22 is a block diagram illustrating an example of components of awireless device according to implementations of the present disclosure.

DETAILED DESCRIPTION

Implementations disclosed herein enable transmitting and receiving adownlink data channel. In a fifth generation (5G) wireless communicationsystem, a bandwidth part (BWP) may be changed dynamically, for example,to achieve improved energy savings and/or load balancing throughRF/baseband switching. In addition, Hybrid Automatic Repeat reQuestAcknowledgment (HARQ-ACK) codebook configuration, CSI reporting, and thelike can be changed based on the change of the BWP. In particular, whenCarrier Aggregation (CA) is implemented using multiple BWPs, it may benecessary to define the HARQ-ACK codebook configuration and the CSIconfiguration method according to the change in BWP.

According to the present disclosure, when different BWPs use asemi-static HARQ-ACK codebook and a dynamic HARQ-ACK codebook, and use atransport block (TB)-based HARQ-ACK and a code block group (CBG)-basedHARQ-ACK, implementations are disclosed herein that enable HARQ-ACKtransmission in a case where HARQ-ACK transmission methods are differentfor each BWP. In addition, implementations disclosed herein enable aHARQ-ACK transmission method in the process of changing BWPs due to BWPswitching. Implementations of the present disclosure are not limited tothe scenario of HARQ-ACK transmission, and may be extended to otherUplink Control Information (UCI) transmissions, such as channel stateinformation (CSI).

In some scenarios, a user equipment (UE) receives downlink controlinformation (DCI) in a first BWP, and the DCI schedules a PDSCHreception in a second BWP, after a BWP change. Implementations aredisclosed herein for interpreting the information contained in the DCIfor transmitting and receiving the PDSCH.

According to the present disclosure, in some implementations, even whena first BWP before a BWP change is different from and a second BWP afterthe BWP change, implementations disclosed herein can provide stabletransmission and reception of the downlink data channel withoutambiguity.

Hereinafter, the structure, operation and other features of the presentdisclosure will be readily understood by the implementations of thepresent disclosure described with reference to the accompanyingdrawings. The implementations described below are examples in whichtechnical features of the present disclosure are applied to a 3GPPsystem.

Although the present specification describes an implementation of thepresent disclosure using an LTE system, an LTE-A system, and an NRsystem, implementations of the present disclosure may be applied to anysuitable communication system that is compliant with the abovestandards.

Also, although the present disclosure utilizes specific terminology suchas a remote radio head (RRH), an eNB, a transmission point (TP), areception point (RP), a relay, and the like, implementations of thepresent disclosure may be applied to more general systems that utilizeanalogous features.

3GPP-based communication standards typically include downlink physicalchannels corresponding to resource elements carrying informationoriginating from an upper layer, as well as downlink physical signalsused by the physical layer but corresponding to resource elements notcarrying information originated from an upper layer.

For example, downlink physical channels may include a Physical DownlinkShared Channel (PDSCH), a Physical Broadcast Channel (PBCH), a PhysicalMulticast Channel (PMCH), a Physical Control Format Indicator Channel aphysical downlink control channel (PDCCH), and a physical hybrid ARQindicator channel (PHICH).

Downlink physical signals may include a reference signal and asynchronization signal. A reference signal (RS), also referred to as apilot, refers to a signal of a particular and predetermined waveformthat is known to the gNB and the UE. Examples of downlink referencesignals include, for example, a cell specific RS, a UE-specific RS(UE-RS), a positioning RS (PRS), and channel state information RS(CSI-RS).

For uplink communications, 3GPP-based communication standards typicallyinclude uplink physical channels corresponding to resource elementscarrying information originating from an upper layer, as well as uplinkphysical signals corresponding to resource elements used by the physicallayer but not carrying information originated from an upper layer.

For example, uplink physical channels include a physical uplink sharedchannel (PUSCH), a physical uplink control channel (PUCCH), a physicalrandom access channel (PRACH), a demodulation reference signal (DMRS)for the uplink control/data signal, and a sounding reference signal(SRS) used for the uplink channel measurement.

In the present disclosure, a Physical Downlink Control Channel (PDCCH),a Physical Control Format Indicator CHannel (PCFICH), a Physical HybridAutomatic Repeat Request Indicator CHannel (PHICH), and a PhysicalDownlink Shared CHannel (PDSCH), a Physical Uplink Control CHannel(PUCCH), a Physical Uplink Control Channel (PUSCH), a Physical UplinkControl Channel (PUSCH), and a Physical Uplink Control Channel (PUSCH)(Uplink Shared CHannel)/PRACH (Physical Random Access CHannel) refers toa set of time-frequency resources or a set of resource elements thatcarry Downlink Control Information (DCI), Control Format Indicator(CFI), downlink ACKnowlegement/Negative ACK (DL ACK/NACK), and DL data.

Hereinafter, the expression that a user equipment (UE) transmits thePUCCH/PUSCH/PRACH is used in the same sense as to transmit the uplinkcontrol information/uplink data/random access signal on thePUSCH/PUCCH/PRACH, respectively. Also, the expression that a gNode B(gNB) transmits PDCCH/PCFICH/PHICH/PDSCH is used in the same sense as totransmit downlink data/control information on thePDCCH/PCFICH/PHICH/PDSCH, respectively. In the following description, anOFDM symbol/subcarrier/RE allocated with CRS/DMRS/CSI-RS/SRS/UE-RS isreferred to as CRS/DMRS/CSI-RS/SRS/UE-RS symbol/carrier/subcarrier/RE.For example, an OFDM symbol to which a tracking RS is allocated orconfigured is referred to a “TRS symbol,” a sub-carrier to which a TRSis allocated or configured is referred to as a “TRS subcarrier,” and aRE to which a TRS is allocated or configured is referred to as a “TRSRE.” In addition, a subframe configured for TRS transmission is referredto as a “TRS subframe.” A subframe in which a broadcast signal istransmitted is called a “broadcast subframe” or a “PBCH subframe,” and asubframe in which a synchronization signal (for example, PSS and/or SSS)is transmitted is referred to as a “synchronization signal subframe” ora “PSS/SSS subframe.” The OFDM symbols/subcarriers/REs to which PSS/SSSis configured or set are referred to as “PSS/SSS symbol/subcarrier/RE,”respectively.

In the present disclosure, a CRS port, UE-RS port, CSI-RS port, and TRSport are respectively configured as an antenna port configured totransmit CRS, an antenna port configured to transmit UE-RS, an antennaport configured to transmit CSI-RS, and an antenna port configured totransmit TRS. The antenna ports configured to transmit CRSs can bedistinguished from each other by the location of the REs occupied by theCRS according to the CRS ports, the antenna ports configured to transmitUE-RSs can be distinguished from each other by the location of the REsoccupied by the UE-RS according to the UE-RS ports, and the antennaports configured to transmit the CSI-RSs can be distinguished from eachother by the positions of the REs occupied by the CSI-RS according tothe CSI-RS ports. Therefore, the term CRS/UE-RS/CSI-RS/TRS port is alsoused as a term for a pattern of REs occupied by CRS/UE-RS/CSI-RS/TRSwithin a certain resource area.

FIG. 1 is a diagram illustrating an example of a control plane and auser plane structure of a radio interface protocol between a UE and anE-UTRAN based on the 3GPP radio access network standard. The controlplane refers to a path through which control messages used by a UE and anetwork are transmitted. The user plane refers to a path through whichdata generated in the application layer, for example, voice data orInternet packet data, is transmitted.

The physical (PHY) layer, which is the first layer, provides aninformation transfer service to an upper layer using a physical channel.The physical layer is connected to the upper Medium Access Control (MAC)layer through a transmission channel (Transport Channel). Data movesbetween the MAC layer and the PHY layer over the transmission channel.Data is transferred between a transmitting side (e.g., transmittingdevice) and a receiving side (e.g., receiving device) at the physicallayer through the physical channel. The physical channel utilizes timeand frequency as radio resources. For example, the physical channel maybe modulated according to Orthogonal Frequency Division Multiple Access(OFDMA) in a downlink, and may be modulated according to Single CarrierFrequency Division Multiple Access (SC-FDMA) an uplink.

The Medium Access Control (MAC) layer of the second layer provides aservice to a radio link control (RLC) layer, which is an upper layer,through a logical channel. The RLC layer of the second layer supportsreliable data transmission. In some implementations, the function of theRLC layer may be implemented as a functional block in the MAC. ThePacket Data Convergence Protocol (PDCP) layer of the second layerperforms a header compression function to reduce the amount of controlinformation and efficiently transmit IP packets, such as IPv4 and IPv6packets, in a wireless interface with a narrow bandwidth.

The Radio Resource Control (RRC) layer located at the bottom of thethird layer is, in some implementations, defined only in the controlplane. The RRC layer is responsible for the control of logical channels,transmission channels, and physical channels in connection with theconfiguration, re-configuration and release of radio bearers. A “radiobearer” refers to a service provided by the second layer for datatransmission between a UE and a network. To this end, the terminal andthe RRC layer of the network may exchange RRC messages with each other.If there is an RRC connection between the UE and the RRC layer of thenetwork, then the UE is in an “RRC Connected Mode,” and otherwise the UEis in an “RRC Idle Mode.” The Non-Access Stratum (NAS) layer at the topof the RRC layer performs functions such as session management andmobility management.

A downlink transmission channel for transmitting data from a network toa terminal (e.g., a UE) includes, for example, a BCH (Broadcast Channel)for transmitting system information, a PCH (Paging Channel) fortransmitting a paging message, a downlink SCH (Shared Channel) fortransmitting user traffic and control messages. In the case of a trafficor control message of a downlink multicast or broadcast service, thesemessages may be transmitted through a downlink SCH, or may betransmitted via a separate downlink multicast channel (MCH). In someimplementations, the uplink transmission channel for transmitting datafrom the UE to the network includes, for example, a RACH (Random AccessChannel) for transmitting an initial control message, and an uplink SCH(Shared Channel) for transmitting user traffic or control messages. Alogical channel mapped to a transmission channel includes, for example,a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), aCommon Control Channel (CCCH), a Multicast Control Channel (MCCH), and aMulticast Traffic Channel (MTCH).

FIG. 2 is a diagram showing an example of a physical channel used in a3GPP system and a general signal transmission method using the same.

When the UE is turned on or newly enters a cell, the UE performs aninitial cell search operation, such as synchronizing with the basestation (BS) (S201). To this end, the UE receives a primarysynchronization channel (P-SCH) and a secondary synchronization channel(S-SCH) from the BS, synchronizes with the BS, and acquires informationsuch as a cell ID. Then, the UE can receive the physical broadcastchannel from the BS and acquire the in-cell broadcast information. Insome implementations, the UE can receive a downlink reference signal (DLRS) in the initial cell search step, to check the downlink channelstate.

Upon completion of the initial cell search, the UE receives moredetailed system information by receiving a Physical Downlink ControlChannel (PDCCH), as well as a Physical Downlink Control Channel (PDSCH)according to the information on the PDCCH (S202).

In some implementations, if the US is connecting to a base station (BS)as an initial connection, or if there is no radio resource for signaltransmission, then the UE can perform a random access procedure (RACH)for the BS (steps S203 to S206). To this end, the UE transmits aspecific sequence through a Physical Random Access Channel (PRACH) as apreamble (S203 and S205), and receives a response message to thatpreamble on the PDCCH and the corresponding PDSCH (S204 and S206). Inscenarios of contention-based RACH, a contention resolution procedurecan be additionally performed.

The UE having performed the above procedure may then perform receptionof PDCCH/PDSCH (S207), and transmission of physical uplink sharedchannel (PUSCH)/physical uplink control channel Control Channel (PUCCH)(S208). For example, the UE may receive downlink control information(DCI) through the PDCCH. In such scenarios, the DCI may include controlinformation, such as resource allocation information for the UE, and theDCI formats may be different according to the purpose of use.

In some implementations, the control information transmitted by the UEto the Node B via the uplink or received from the Node B by the UEincludes, for example, a downlink/uplink ACK/NACK signal, a channelquality indicator (CQI), a precoding matrix index (PMI), a rankindicator (RI), and the like. In some systems, e.g., those compatiblewith the 3GPP LTE standard, the UE may transmit control information suchas CQI/PMI/RI as described above through PUSCH and/or PUCCH.

FIG. 3 illustrates an example of the structure of a radio frame used inNR.

In NR, uplink and downlink transmission are composed of frames. Theradio frame may have a length of 10 ms and may be defined as two 5-mshalf-frames (HFs). Each half-frame may be defined as five 1-ms subframes(SFs). A subframe may be divided into one or more slots, and the numberof slots in a subframe may depend on SCS (Subcarrier Spacing). Each slotmay include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).In some implementations, if a CP is used, then each slot contains 14symbols. If an extended CP is used, then each slot contains 12 symbols.The symbol may include, for example, an OFDM symbol (or a CP-OFDMsymbol) and an SC-FDMA symbol (or a DFT-s-OFDM symbol).

Table 1 illustrates an example of a normal CP, where the number ofsymbols per slot, the number of slots per frame, and the number of slotsper subframe are different according to the SCS.

TABLE 1 SCS (15 * 2 {circumflex over ( )} u) N^(slot) symb N^(frame,u)slot N^(subframe,u) slot  15 KHz (u = 0) 14 10 One  30 KHz (u = 1) 14 202  60 KHz (u = 2) 14 40 4 120 KHz (u = 3) 14 80 8 240 KHz (u = 4) 14 16016 where N ^(slot) symb is the number of symbols per slot, N^(frame,u)slot is the number of slots per frame, and N^(subframe,u) slot is thenumber of slots per subframe.

Table 2 illustrates an example of extended CP, where the number ofsymbols per slot, the number of slots per frame, and the number of slotsper subframe are different according to the SCS.

TABLE 2 SCS (15 * 2 {circumflex over ( )} u) N^(slot) symb N^(frame,u)slot N^(subframe,u) slot 60 KHz (u = 2) 12 40 4

In an NR system, OFDM (A) numerology (e.g., SCS, CP length, etc.) may beset differently among a plurality of cells for one UE. Accordingly, the(absolute time) interval of a time resource (e.g., SF, slot or TTI) (forconvenience, TU (Time Unit)) composed of the same number of symbols canbe set differently between merged cells.

FIG. 4 illustrates an example of a slot structure of an NR frame. A slotincludes a plurality of symbols in the time domain. For example, in thecase of a normal CP, one slot includes seven symbols, whereas in thecase of an extended CP, one slot includes six symbols.

A carrier wave includes a plurality of subcarriers in the frequencydomain. An RB (Resource Block) is defined as a plurality (e.g., 12) ofconsecutive subcarriers in the frequency domain. A BWP (Bandwidth Part)is defined as a plurality of consecutive RBs (or physical RBs) in thefrequency domain, and can correspond to one numerology (e.g., one SCS,one CP length, etc.). Each carrier may include up to N (e.g., 5) BWPs.

In some implementations, data communication is performed through anactivated BWP, and only one BWP may be activated for one UE. In aresource grid representation, each element of the resource grid isreferred to as a Resource Element (RE), to which one complex symbol canbe mapped.

FIG. 5 illustrates an example of the structure of a self-contained slot.In an NR system, a frame is characterized by a self-contained structurein which a DL control channel, DL or UL data, a UL control channel,etc., can all be contained in one slot. For example, the first N symbolsin a slot may be used to transmit a DL control channel (hereinafterreferred to as a DL control area), and the last M symbols in a slot maybe used to transmit UL control channels (hereinafter referred to as a ULcontrol area). N and M may each be an integer of 0 or more.

A resource area (hereinafter referred to as a data area) between the DLcontrol area and the UL control area may be used for DL datatransmission or UL data transmission. For example, the followingconfiguration may be implemented. Each section is listed inchronological order.

1. DL only configuration

2. UL only configuration

3. Mixed UL-DL configuration

DL area+Guard period (GP)+UL control area

DL control area+GP+UL area

DL area: (i) DL data area, (ii) DL control area+DL data area

UL area: (i) UL data area, (ii) UL data area+UL control area

The PDCCH may be transmitted in the DL control region, and the PDSCH maybe transmitted in the DL data region. Analogously, in the UL controlregion, the PUCCH may be transmitted, and in the UL data region, thePUSCH can be transmitted. The PDCCH may transmit Downlink ControlInformation (DCI), such as, for example, DL data scheduling information,UL data scheduling information, and the like. The PUCCH may transmitUplink Control Information (UCI), such as, for example, ACK/NACKinformation, DL CSI information, and Scheduling Request (SR), and thelike.

The GP provides a time gap in the process of switching from atransmission mode to a reception mode, or switching from the receptionmode to the transmission mode. A portion of symbols within a subframecan be set to GP for switching from DL to UL.

In some implementations, an NR system may utilize a high-frequency band,e.g., a millimeter-frequency band of 6 GHz or more, in order to transmitdata while maintaining a high data rate for a large number of users in awide frequency band. However, in such scenarios, themillimeter-frequency band may have a frequency characteristic in whichthe signal attenuation due to distance is very sharp due to thehigh-frequency nature of the band. Therefore, to compensate for suchsudden attenuation characteristics, an NR system that utilizes at leasta band of 6 GHz may transmit a signal beam in a specific direction,rather than in all directions, so as to transmit a narrow beam. In suchscenarios where a service is performed using narrow beams, since a rangeof a single base station may be narrowed, the base station may collect aplurality of narrow beams and provide services over a wide band thatencompasses the plurality of narrow beams.

In the millimeter frequency band, that is, in the millimeter wave (mmW)band, wavelengths are typically shortened, and this allows a pluralityof antenna elements to be installed in the same area. For example, in a30 GHz band with a wavelength of about 1 cm, a total of 100 antennaelements can be installed in a 5-by-5 cm panel in a two-dimensionalarray at 0.5 lambda (wavelength) intervals. Therefore, in mmW, coverageor throughput may be increased by increasing the beamforming gainthrough a plurality of antenna elements.

In some implementations, as a technique for forming a narrow beam in themillimeter frequency band, beam forming be may implemented in whichenergy is raised only in a specific direction by transmitting the samesignal using an appropriate phase difference to a large number ofantennas in a base station or a UE. Such beamforming schemes include (i)digital beamforming that creates a phase difference in a digitalbaseband signal, (ii) analog beamforming that creates a phase differenceusing a time delay (i.e., a cyclic shift) on the modulated analogsignal, and (iii) hybrid beamforming using both digital beamforming andanalog beamforming.

In scenarios where a transceiver unit (TXRU) is provided to enabletransmission power and phase adjustment for each antenna element, thenindependent beamforming for each frequency resource may be implemented.However, problems may arise in that the TXRU may not be cost-effectivein terms of installing numerous antenna elements of 100 or more. Forexample, a millimeter frequency band may require a large number ofantennas to compensate for sudden attenuation characteristics. In suchscenarios, digital beamforming may require a number of RF components(e.g., a digital-to-analog converter (DAC)), mixers, power amplifiers,linear amplifiers, and the like, in a number that is a many as thenumber of antennas. As such, digital beamforming in the millimeterfrequency band may face problems in that the price of communicationdevices may increase.

Therefore, when a large number of antennas is required, such as in themillimeter frequency band, implementations may utilize analogbeamforming or hybrid beamforming. In the analog beamforming scheme, aplurality of antenna elements are mapped to one TXRU and the directionof a beam is adjusted by an analog phase shifter. In some scenarios,such an analog beamforming scheme may have a disadvantage in that it cangenerate only one beam direction in the entire band, and may not be ableto perform frequency selective beamforming (BF). Hybrid BF is anintermediate form of digital BF and analog BF, and has a number (e.g.,B) of TXRUs that are fewer than the number (e.g., Q) of antennaelements. In the case of hybrid BF, the number of beams that can betransmitted at the same time may be limited to B or less, althoughscenarios may vary depending on the connection method of the B TXRUs andQ antenna elements.

As mentioned above, since digital beamforming performs signal processingon a digital baseband signal to be transmitted or received, it ispossible to transmit or receive signals in various directionssimultaneously using multiple beams. By contrast, since analogbeamforming performs beamforming in the modulated state of an analogsignal to be transmitted or received, it cannot simultaneously transmitor receive signals in a plurality of directions beyond the range coveredby one beam.

In general, a base station communicates with a plurality of users (UEs)at the same time using a broadband transmission or a multi-antennacharacteristic. When a base station uses analog or hybrid beamformingand forms an analog beam in one beam direction, the base station mayonly be able to communicate with users included in the same analog beamdirection due to the characteristics of analog beamforming.

Implementations disclosed herein provide RACH resource allocation andresource utilization for a base station that may, in some scenarios,mitigate such constraint inconsistencies caused by analog beamforming orhybrid beamforming characteristics.

FIG. 6 illustrates an example of a hybrid beamforming structure in termsof a transceiver unit (TXRU) and a physical antenna.

In scenarios where multiple antennas are utilized, a hybrid beamformingtechnique, which combines digital beamforming and analog beamforming,may be implemented. In analog beamforming (or RF beamforming), atransceiver (or an RF unit) performs precoding (or combining). In hybridbeamforming, a baseband unit and a transceiver (or RF unit) performprecoding (or combining), respectively. This may have the advantage ofachieving performance that is close to digital beamforming, whilereducing the number of RF chains and the number of D/A (or A/D)converters.

For convenience, the hybrid beamforming structure may be represented byN TXRUs and M physical antennas. Digital beamforming for L data layersto be transmitted at the transmitting end may be represented by anN-by-L matrix. The N converted digital signals may then be convertedinto analog signals via a TXRU, and then analog beamforming representedby an M-by-N matrix is applied.

In the example of FIG. 6, the number of digital beams is L and thenumber of analog beams is N. Further, in an NR system, a base stationmay be configured to change analog beamforming in units of symbols, andmay thus provide more efficient beamforming for UEs located in aspecific region. Furthermore, when N TXRU and M RF antennas are definedas one antenna panel, a plurality of antenna panels may be implementedto which independent hybrid beamforming is applicable in the NR system.When a base station utilizes a plurality of analog beams, an analog beamthat is advantageous for signal reception may be different for each UE.Therefore, in some scenarios, such as for a synchronous signal, systeminformation, paging, etc., a beam-sweeping operation may be implementedin which a base station changes multiple analog beams on asymbol-by-symbol basis for a specific slot or subframe, to providereception opportunities to multiple UEs.

FIG. 7 is a diagram illustrating an example of a beam sweeping operationfor a synchronization signal and system information in a downlinktransmission process.

In the example of FIG. 7, a physical resource or a physical channelthrough which system information of the New RAT system is broadcast isreferred to as xPBCH (physical broadcast channel). In someimplementations, analog beams belonging to different antenna panels maybe simultaneously transmitted within one symbol. In order to measure thechannel for each analog beam, as shown in FIG. 7, implementations mayutilize a Beam Reference Signal (BRS), which is a reference signal thatis transmitted for a corresponding single analog beam. In somescenarios, a BRS may be defined for a plurality of antenna ports, andeach antenna port of the BRS may correspond to a single analog beam. Insome implementations, unlike the BRS, the synchronization signal or thexPBCH may be transmitted for all the analog beams included in the analogbeam group, so that any UE can receive it well.

FIG. 8 illustrates an example of a cell of a new radio access technology(NR) system.

Referring to the example of FIG. 8, in some scenarios, an NR system mayimplement a plurality of TRPs that constitute one cell, unlike ascenario where one base station forms one cell in a wirelesscommunication system. In scenarios where a plurality of TRPs constituteone cell, even if the TRP for serving the UE is changed, there may be anadvantage in that seamless communication can be provided and mobilitymanagement of the UE is facilitated.

In some systems, e.g., systems that are compatible with LTE/LTE-A, thePSS/SSS may be transmitted in an omni-direction. In someimplementations, a gNB applying mmWave beam-forms a signal such as aPSS/SSS/PBCH while rotating the beam direction in an omnidirectionalmanner. The transmission/reception of signals while rotating the beamdirection is referred to as “beam sweeping” or “beam scanning.” In thepresent disclosure, beam sweeping refers to the transmitter-sidebehavior, and beam scanning refers to the receiver-side behavior.

For example, assuming that the gNB can have a maximum of N beamdirections, the gNB may transmit signals (e.g., PSS/SSS/PBCH) across Nbeam directions, respectively. In other words, the gNB may transmitsynchronization signals (e.g., PSS/SSS/PBCH) for each direction whilesweeping directions that the gNB can implement or support.Alternatively, if the gNB can form N beams, then several beams may bebundled into one beam group, and the PSS/SSS/PBCH may be transmittedand/or received for each beam group. Each beam group may include one ormore beams.

A signal (e.g., PSS/SSS/PBCH) that is transmitted in the same directionmay be defined as one SS block, and a plurality of SS blocks may beimplemented in one cell. In scenarios where there are a plurality of SSblocks, an SS block index may be utilized for distinguishing each SSblock. For example, when a PSS/SSS/PBCH is transmitted in 10 beamdirections in one system, then a PSS/SSS/PBCH in the same direction canconstitute one SS block. In such a system, 10 SS blocks may beunderstood as being implemented. In the present disclosure, the beamindex can be interpreted as an SS block index.

Bandwidth Part (BWP)

In some implementations, an NR system may support a per-carrierbandwidth of up to 400 MHz per carrier. If a UE operating on such awideband carrier always operates with the radio frequency moduleturned-on for the entire carrier wave, then the UE's battery consumptionmay increase. Also, different usage scenarios (e.g., eMBB, URLLC, mMTC,V2X, etc.) operating within a single wideband carrier, differentamplitudes (e.g., subcarrier spacing) may be supported for eachfrequency band within the corresponding carrier. Furthermore, thecapability for the maximum bandwidth per UE may be different.

In consideration of these factors, a base station may instruct a UE tooperate only in a part of the bandwidth, rather than over the entirebandwidth of the wideband carrier. The corresponding bandwidth in whichthe UE is instructed to operate is referred to as a “bandwidth part”(BWP). In the frequency domain, the BWP is a subset of contiguous commonresource blocks defined for the numerology i in the bandwidth part i onthe carrier, and one numerology (e.g., subcarrier spacing, CP length,slot/mini-slot duration) can be set.

In some implementations, a base station may configure one or more BWPsin one carrier wave configured for a UE. Alternatively, some UEs may bemoved to another BWP for load balancing when multiple UEs overload aparticular BWP. Alternatively, consideration may be given to frequencydomain inter-cell interference cancellation between neighboring cells,and BWPs on both sides of the cell may be configured in the same slot byexcluding some of the spectrums of the entire bandwidth.

For example, the base station may configure at least one DL/UL BWP to aUE associated with a wideband carrier, and activate at least one DL/ULBWP among DL/UL BWPs set at a specific point in time. The base stationmay instruct to switch to the BWP or configured the timer value so thatthe UE switches to the designated DL/UL BWP when the timer expires. Asexamples, the base station may transmit at least one DL/UL BWP ofmultiple DL/UL BWPs (e.g., by L1 signaling, MAC CE, or RRC signaling) orby switching to another configured DL/UL BWP (e.g., by L1 signaling, aMAC control element (CE) as a MAC layer control signal, or RRCsignaling) to allow the UE to switch to a predetermined DL/UL BWP whenthe timer expires.

In some implementations, DCI format 1_1 or DCI format 0_1 may be used bythe base station to instruct the UE to switch to another configuredDL/UL BWP. The activated DL/UL BWP may be specifically referred to asthe “active DL/UL BWP.” If the UE is in an initial access procedure, orif the UE has not yet setup an RRC connection, then be UE may notreceive the setting for the DL/UL BWP. In such situations, the DL/UL BWPassumed by the UE is called the initial active DL/UL BWP.

As used herein, the term “DL BWP” refers to a BWP fortransmitting/receiving a downlink signal (e.g., PDCCH and/or PDSCH), andthe term “UL BWP” refers to a BWP for transmitting/receiving an uplinksignal (e.g., PUCCH and/or PUSCH).

Hybrid Automatic and the Repeat reQuest (HARQ)

HARQ-ACK operation with respect to UE operation for reporting controlinformation will be described next. The HARQ-ACK is informationindicating whether the UE has successfully received a physical downlinkchannel. If the UE has successfully received the physical downlinkchannel, then the UE sends an acknowledgment (ACK) feedback to the basestation. If the UE does not successfully receive the physical downlinkchannel, then the UE sends a negative acknowledgment (NACK) feedback tothe base station. The HARQ in NR supports one bit of HARQ-ACK feedbackper transport block.

FIG. 9 is a diagram showing an example of the HARQ-ACK timing.

In the example of FIG. 9, K0 denotes the number of slots starting fromthe slot having the PDCCH carrying the DL allocation (i.e., the DLgrant) to the slot having the corresponding PDSCH transmission. K1denotes the number of slots starting from the slot of the PDSCH to theslot of the corresponding HARQ-ACK transmission. K2 denotes the numberof slots starting from the slot having the PDCCH (carrying the UL grant)to the slot having the corresponding PUSCH transmission. That is, K0,K1, and K2 can be summarized as shown in Table 3 below.

TABLE 3 A B K0 DL scheduling DCI Corresponding DL data transmission K1DL data reception Corresponding HARQ-ACK K2 UL scheduling DCICorresponding UL data transmission

The base station can provide the UE with the HARQ-ACK feedback timingdynamically in DCI or semi-statically via RRC signaling.

In some implementations e.g., systems that are compatible with NR,different minimum HARQ processing times may be supported between UEs.The HARQ processing time includes the delay between the DL datareception timing and the corresponding HARQ-ACK transmission timing andthe delay between the UL grant reception timing and the corresponding ULdata transmission timing. The UE transmits, to the base station,information regarding the capability of its minimum HARQ processingtime. From the UE point of view, HARQ ACK/NACK feedback for multiple DLtransmissions in the time domain can be transmitted in one ULdata/control domain. The timing between the reception of the DL data andthe corresponding ACK is indicated by the DCI.

Unlike some systems (e.g., some systems that are compatible with LTE) inwhich the HARQ process is performed for each transport block orcodeword, implementations disclosed herein (which may be compatible withNR) support transmission based on code block groups withsingle/multi-bit HARQ-ACK feedback. The transport block can be mapped toone or more CBs depending on the size of the TB. For example, in thechannel coding process, a CRC code is attached to the TB. If the TB withthe CRC is not larger than the predetermined size, the TB with the CRCcorresponds to one code block. If the TB with the CRC is larger than thepredetermined size, TB is segmented into a plurality of CBs. In the NRsystem, the UE may be configured to receive CBG-based transmissions, andthe retransmission may be scheduled to carry a subset of all CBs of theTB.

Code Block Group (CBG)-Based HARQ Process

In some systems, such as those compatible with LTE, a transport block(TB)-based HARQ process is supported. In systems that are compatiblewith NR, a CBG-based HARQ process is supported with a TB-based HARQprocess.

FIG. 10 illustrates an example of the processing and structure of TB.The example of FIG. 10 may be applied to data of a DL-SCH (SharedChannel), a PCH (Paging Channel), and an MCH (Multicast Channel)transmission channel. Furthermore, UL TB (or data on an UL transportchannel) may be similarly processed.

Referring to the example of FIG. 10, the transmitter performs a CRC(e.g., 24-bit) (TB CRC) for error checking on the TB. Then, thetransmitter can divide the TB+CRC into a plurality of code blocksconsidering the size of the channel encoder. In one example, the maximumsize of a code block in LTE is 6144-bits. Therefore, if the TB size isequal to or less than 6144 bits, the code block is not formed. If the TBsize is greater than 6144 bits, TB is divided into 6144-bit units toconstitute a plurality of code blocks. In each code block, a CRC (e.g.,24-bit) (CB CRC) is added separately for error checking. Each code blockis channel-coded and rate-matched, and then combines to form a codeword.In the TB-based HARQ process, the data scheduling and the HARQ processare performed on a TB basis, and the CB CRC is used to determine theearly termination of the TB decoding.

FIG. 11 illustrates an example of a CBG-based HARQ process. In theCBG-based HARQ process, the data scheduling and the HARQ process can beperformed in TB units.

Referring to the example of FIG. 11, a UE may receive, from a basestation (e.g., Node B), information regarding a number M of code blockgroups per transport block, and this information may be received throughan upper layer signal (e.g., RRC signal) (S1102). Thereafter, the UE mayreceive initial data transmission (via the PDSCH) from the Node B(S1104). The data may include a transmission block (TB), and the TB mayinclude a plurality of code blocks (CBs), and the plurality of CBs maybe grouped into one or more code block groups (CBGs) within the TB.Here, some of the CBGs may include a number ceiling (K/M) of CBs, andthe remaining CBs may include a number flooring (K/M) of CBs. Theparameter K represents the number of CBs in the data.

Based on whether the UE correctly received the data, the UE can provide,as feedback, CBG-based ACK/NACK information regarding the data to thebase station (S1106), and the base station can perform dataretransmission of the data in units of CBGs (S1108). The A/N informationmay be transmitted via PUCCH or PUSCH. In some implementations, the A/Ninformation includes a plurality of A/N bits for data, where each A/Nbit represents each A/N response that is generated for each CBG. In somescenarios, the payload size of the A/N information may be kept the samebased on M, regardless of the number of CBGs constituting the data.

Dynamic/Semi-Static HARQ-ACK Codebook Scheme

NR supports a dynamic HARQ-ACK codebook scheme and a semi-staticHARQ-ACK codebook scheme. The HARQ-ACK (or A/N) codebook may be replacedwith an HARQ-ACK payload.

When the dynamic HARQ-ACK codebook scheme is set, the size of the A/Npayload varies depending on the number of actually scheduled DL data. Tothis end, the PDCCH associated with DL scheduling includes a counter-DAI(Downlink Assignment Index) and a total-DAI. The counter-DAI indicatesthe {CC, Slot} scheduling order value calculated in CC (ComponentCarrier) (or cell) -first manner and is used to designate the positionof the A/N bit within the A/N codebook. The total-DAI indicates thecumulative value of slot-by-slot scheduling up to the current slot andis used to determine the size of the A/N codebook.

When the semi-static A/N codebook scheme is set, the size of the A/Ncodebook is fixed (at a maximum value) regardless of the actual numberof scheduled DL data. Specifically, the (maximum) A/N payload (size)transmitted through one PUCCH in one slot is used for all CCs set to theUE and all the DL scheduling slots for which the A/N transmission timingcan be indicated Or a combination of a PDSCH transmission slot or aPDCCH monitoring slot (hereinafter referred to as a bundling window).For example, the DL grant DCI (PDCCH) includes PDSCH-to-A/N timinginformation and the PDSCH-to-A/N timing information may have one of aplurality of values (e.g., k). For example, if the PDSCH is received inslot #m and the PDSCH-to-A/N timing information in the DL grant DCI(PDCCH) scheduling the PDSCH indicates k, then the A/N information forthe PDSCH may be transmitted in slot # (m+k). For example, k being anelement in the set {1, 2, 3, 4, 5, 6, 7, 8} can be given. On the otherhand, when the A/N information is transmitted in the slot #n, then theA/N information may include the maximum A/N possible based on thebundling window. That is, the A/N information of the slot #n may includeA/N corresponding to the slot # (n−k). For example, in the case of kbeing an element of the set {1, 2, 3, 4, 5, 6, 7, 8}, the A/Ninformation of slot #n corresponds to A/N information of slot #(n−8) toslot #(n−1) (i.e., the maximum number of A/N). Here, the A/N informationmay be replaced with an A/N codebook and an A/N payload. Also, a slotcan be understood/substituted as a candidate occasion for receiving DLdata. As illustrated, the bundling window is determined based on thePDSCH-to-A/N timing with respect to the A/N slot and the PDSCH-to-A/Ntiming set has a predefined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}, andupper layer (RRC) signaling.

Hereinafter, a method for transmitting/receiving HARQ-ACK according toan implementation of the present disclosure will be described in detail.

In the 5th generation NR system, the bandwidth part (BWP) is changeddynamically, and may enable energy saving and/or load balancing throughRF/baseband switching.

In addition, HARQ-ACK codebook configuration, CSI reporting, and thelike can be changed based on the change of BWP. Particularly, whenCarrier Aggregation (CA) is applied, BWP is independent It is necessaryto define the HARQ-ACK codebook configuration and the CSI configurationmethod according to the change.

In the present disclosure, for example, when different BWPs use asemi-static HARQ-ACK codebook and a dynamic HARQ-ACK codebook, use aTB-based HARQ-ACK and a CBG-based HARQ-ACK, A HARQ-ACK transmissionmethod in a case where HARQ-ACK transmission methods are different foreach BWP will be described. In addition, a HARQ-ACK transmission methodin the process of changing BWP through BWP switching will be described.Implementations of the present disclosure are not limited to HARQ-ACKtransmission, and may be extended to other UCI transmissions such asCSI.

Basically, the HARQ-ACK feedback transmission method in the NR systemincludes a semi-static HARQ-ACK codebook scheme and a dynamic HARQ-ACKcodebook scheme.

In the case of the semi-static HARQ-ACK codebook scheme, considering allthe PDCCH monitoring occasions associated with a specific PUCCHtransmission time, considering the plurality of PDSCH-to-HARQ-ACKfeedback timings set for the UE, HARQ—The UE can process NACKs for PDSCH(Physical Downlink Shared Channel) that is not scheduled in the PDCCHmonitoring occasions.

Among the PDSCH reception occasions that can expect reception of a PDSCHin a plurality of slots based on a PDSCH-to-HARQ-ACK feedback timingassociated with a specific PUCCH transmission time point (i.e., aHARQ-ACK transmission time point), PDSCH reception occasions other thanPDSCH reception occasions that cannot be scheduled by the PDCCH amongthe PDSCH reception occasions, i.e., PDSCH reception opportunities otherthan the PDSCH reception opportunity that cannot be scheduled by thePDCCH, are referred to as “candidate PDSCH reception opportunities.”.

Among the candidate PDSCH reception occasions, the candidate PDSCHreception occasions that are not scheduled by the actual PDCCHmonitoring occasions and have not received the PDSCH can be processed asNACK.

In some implementations, in the case of the dynamic HARQ-ACK codebookscheme, the total DAI field and/or the counter DAI field is set in theDCI, and generate/transmit HARQ-ACK bits for the PDSCH that is actuallyscheduled by the PDCCH monitoring opportunities based on thecorresponding DAI value.

In some implementations, when carrier aggregation is applied, HARQ-ACKtransmission for a plurality of cells can be multiplexed to one PUCCHand transmitted.

In this case, when the semi-static HARQ-ACK codebook is used, the orderof the HARQ-ACK bits is the order of the PDCCH monitoring opportunitiesfrom the earliest in time, based on the union of the PDCCH monitoringopportunities of each cell. When a dynamic HARQ-ACK codebook is used, asshown in FIG. 13, when a DCI that schedules a PDSCH in a correspondingcell actually exists, the HARQ-HARQ-ACK can be generated based on this.

In some implementations, such as those compatible with NR, CBG-basedretransmission and/or HARQ-ACK feedback can be set for each servingcell, and the number of CBG-based HARQ-ACK bits and/or maximum CBG-basedHARQ-ACK bits can be set for each serving cell. If a semi-staticHARQ-ACK codebook is used, it is necessary to generate a TB-basedHARQ-ACK for each PDCCH monitoring occasion according to whether aCBG-based HARQ-ACK is set for each cell or a number of CBGs and/or amaximum number of CBGs based on the CBG-based HARQ-ACK bit. In someimplementations, the TB-based HARQ-ACK can be generated with 1 bit or 2bits according to the maximum number of TBs.

In the case of using a dynamic HARQ-ACK codebook, as shown in FIG. 14,HARQ-ACK bits are generated based on the TB-based HARQ-ACK for allserving cells, in addition to the serving cells for which CBGtransmission is set, the number of CBGs to be scheduled for each servingcell is generated based on the maximum value of the number of CBGs setin each serving cell. In some implementations, the maximum value of thenumber of CBGs may be two times the maximum number of TBs set. On theother hand, in some systems (e.g., systems that are compatible with NR),the downlink and uplink signals (for example, subcarrier intervals) maybe different. Therefore, when determining the timing between the PDSCHand the HARQ-ACK feedback, it is necessary to consider the difference inthe signaling for the HARQ-ACK transmission and the feedback for thePDSCH. Basically, K1 representing the offset value between the PDSCH andthe PUCCH to which the HARQ-ACK is transmitted is expressed based on thenumerology of the PUCCH. Therefore, if the slot where the last symbol ofthe PDSCH overlaps is n, the PUCCH is transmitted in the slotcorresponding to n+K1. However, if the sub-carrier interval of the PDSCHis smaller than the sub-carrier interval of the PUCCH, the slot based onthe sub-carrier interval of the PUCCH may be different according to thetime-domain resource allocation (time-domain RA) of the time domain.

In this case, a set of row of time-domain RA tables for a plurality ofPDSCH-to-HARQ feedback timings in which the last symbol of the PDSCH ineach PUCCH slot overlaps can be set. More specifically, the last symbolof the PDSCH can be derived from the SLIV of the time-domain RA field.In this case, the last symbol of the PDSCH can be set to be limited tothe last slot of the aggregated slots in consideration of slotaggregation. Alternatively, the maximum value of the number of PDSCH(non-overlapping PDSCH) combinations that do not overlap between thePDSCHs can be set.

On the other hand, if the subcarrier interval of the PDSCH is largerthan the subcarrier interval of the PUCCH, a plurality of slots for thePDSCH may overlap with one slot based on the subcarrier interval of thePUCCH. In this case, the HARQ-ACK codebook can be calculated based onthe maximum number of PDSCHs (non-overlapping PDSCHs) that do notoverlap each slot. Specifically, a set for all PDSCH slots overlapping aspecific PUCCH slot is set, a maximum value of the number of PDSCH(non-overlapping PDSCH) combinations that do not overlap for each PDSCHslot is set and added, and another PDSCH-to-HARQ feedback timing can berepeatedly applied. In this case, considering the slot aggregation, theimplementation can be applied only to the last slot of the aggregatedslot.

By integrating the above-mentioned methods, the followingimplementations may be derived. For example, if the PUCCH is transmittedin the PUCCH slot n, it can constitute a set of SLIV and PDSCH slotcombinations for all PDSCHs in which the last symbol overlaps the PUCCHslot n−k (where k is all values included in K1). In someimplementations, if slot aggregation is set, the last symbol may be thelast symbol corresponding to the last slot among the aggregated slots.The combination of SLIV and PDSCH slots including uplink symbols in theset for SLIV and/or PDSCH slot combination for all PDSCHs in which thelast symbol overlaps can be excluded from the corresponding set. If thePDCCH monitoring occasion corresponding to the SLIV and PDSCH slotcombination is not set, the corresponding SLIV and PDSCH slotcombination may be excluded from the corresponding set. The maximumnumber of non-overlapping PDSCH combinations can be derived by applyingan algorithm for finding non-overlapping PDSCHs within the determinedset by performing the above-described procedure. At this time, themaximum number of combinations can be derived for each PDSCH slot, andif the slot aggregation is used, the derivation method can be modified.

On the other hand, PDCCH monitoring occasion may be different for eachDCI format. For example, the PDCCH monitoring occasion of DCI format 1_0may be composed of a subset of PDCCH monitoring occasions of DCI format1_1. In this case, the time-domain resource allocation set may bedifferent according to the DCI format.

Therefore, the HARQ-ACK codebook configuration scheme can be madedifferent according to the DCI format. For example, if only the DCIformat 1_1 is considered by the PDCCH monitoring occasion, then theHARQ-ACK codebook can be configured based on the rows of the time-domainRA table that can be indicated in the DCI format 1_1. On the other hand,when DCI format 1_1 and DCI format 1_0 can be monitored by PDCCHmonitoring occasion, the rows of time-domain RA table which can beindicated in DCI format 1_1 and the rows of time the HARQ-ACK codebookcan be constructed based on the union of the -domain RA tables.

For example, a set of PDSCH time-domain RA table rows and DCI formatpair (format pair) can be set. For example, when the availability of thePDCCH is determined for each row, the PDCCH monitoring occasion of theDCI format paired with the corresponding row can be checked to set thecorresponding set. That is, PDCCH monitoring occasions of the DCI formatare confirmed based on the offset value K0 between the slots forreceiving the PDSCH from the slot in which the DCI is received whenchecking each row of the time-domain RA table. If there is a PDCCHmonitoring occasion at that point in time, it can be considered whenconstructing a HARQ-ACK codebook, and otherwise excluded from theHARQ-ACK codebook configuration.

On the other hand, the UE can perform PDCCH monitoring only within thecurrently active DL BWP. In some implementations, CORESET and/or searchspace may be independently set for each BWP. The search space mayinclude monitoring occasions on the time axis for the PDCCH.

However, if the PDCCH monitoring occasions differ according to the BWP,the HARQ-ACK codebook configuration may also have to be changeddynamically. Also, the value range of the PDSCH-to-HARQ-ACK feedbacktiming can be set independently for each BWP, and the HARQ-ACK codebookconfiguration can be changed even in this case.

When the BWP is changed, an interval in which the HARQ-ACK codebookconfiguration is ambiguous may occur. For example, when a plurality ofPDCCH monitoring opportunities associated with a HARQ feedback timepoint of a pre-change BWP and a plurality of PDCCH monitoringopportunities associated with a HARQ feedback time point of apost-change BWP overlap, there may be ambiguity in the HARQ-ACK codebookconfiguration in the overlapping PDCCH monitoring opportunities.

In some implementations, the bits configuring the HARQ-ACK codebook sizeor the HARQ-ACK codebook may be variously changed according tocircumstances. For example, a PDSCH-to-HARQ-ACK timing set is set in {4,5, 6, 7} slots in BWP # (timing set) is set in {4, 6} slots.

For example, when transmitting HARQ-ACK feedback in slot n, it isassumed that it operates in BWP #1 until slot n−4 and operates as BWP #2in slot n−4. In this case, the UE may be ambiguous whether to transmit a4-bit HARQ-ACK for slots n−7, n−6, n−5, and n−4 and/or a 2-bit HARQ-ACKfor slots n−6 and n−4 in slot n. In particular, considering the CAsituation, the overall HARQ-ACK codebook configuration may need to bechanged as the size of the HARQ-ACK changes. However, thePDSCH-to-HARQ-ACK timing aggregation relationship according to the aboveassumption may be extended by combining according to the PDCCH-to-PDSCHtiming.

Now, more specific implementations of a HARQ-ACK codebook constructionmethod according to BWP switching will be described.

First, the operation procedure of the UE, the BS, and the networkaccording to the implementation of the present disclosure will bedescribed with reference to FIGS. 15 to 17.

FIG. 15 is a flowchart illustrating an example of an operation of a UEaccording to an implementation of the present disclosure. Referring toFIG. 15, the UE may receive a plurality of BWPs for receiving a downlinksignal from a base station (S1501). In some implementations, theplurality of BWPs may be set through upper layer signaling. Then, the UEreceives, from the base station, DCI and/or higher layer signaling foractivating the first BWP among the plurality of BWPs (S1503), andreceives the first PDSCH through the activated first BWP (S1505).Thereafter, the UE receives, from the base station, DCI for changing theactive BWP from the first BWP to the second BWP (S1507), and receivesthe second PDSCH through the second active BWP (S1509).

Then, the UE transmits HARQ-ACK for at least one of (i) the first PDSCHreceived through the BWP before change or (ii) the second PDSCH receivedthrough the changed BWP (S1511). In some implementations, the method ofconfiguring the HARQ-ACK and a method of transmitting can be performedaccording to Implementations 1 to 4, described further below.

Referring to FIG. 16, an example of an operation of a base stationaccording to an implementation of the present disclosure will bedescribed. In operation S1601, a base station may configure a pluralityof BWPs for downlink signal transmission to a UE. In someimplementations, the plurality of BWPs may be configured through higherlayer signaling. The base station transmits, to the UE, the DCI and/orhigher layer signaling for activating the first BWP among the pluralityof BWPs (S1603), and transmits the first PDSCH through the activatedfirst BWP (S1605). Thereafter, the base station transmit, to the UE, theDCI for changing the active BWP from the first BWP to the second BWP(S1607), and transmits the second PDSCH through the second active BWP(S1609).

The base station receives from the UE an HARQ-ACK for at least one of(i) the first PDSCH transmitted through the BWP before change, or (ii)the second PDSCH transmitted through the changed BWP (S1611). In someimplementations, the HARQ-ACK is configured and a receiving methodaccording to the first to fourth implementations to be described furtherbelow.

Considering the operations of FIGS. 15 and 16 from the networkperspective in FIG. 17, the base station configures a plurality of BWPsfor downlink signal transmission to the UE through upper layer signaling(S1701), transmits the BWPs of the plurality of BWPs, and transmits theDCI and/or higher layer signaling for activating the first BWP to the UE(S1703). Then, the base station transmits the first PDSCH through theactivated first BWP (S1705). Then, the base station transmits the DCIfor changing the active BWP from the first BWP to the second BWP to theUE (S1707), and transmits the second PDSCH through the second active BWP(S1709).

The UE transmits, to the base station, HARQ-ACK for at least one of (i)the first PDSCH that was transmitted through the BWP before the BWPchange, or (ii) the second PDSCH that was transmitted through the BWPafter the BWP change (S1711). In some implementations, the UE configuresthe HARQ-ACK and a receiving method according to the first to fourthimplementations to be described further below.

Implementation 1

When using a semi-static HARQ-ACK codebook, a UE does not expect the BWPto change. Alternatively, the UE may expect that the PDCCH monitoringoccasion set or the DL association set associated with the HARQ-ACKfeedback is not changed even if the BWP is changed.

In some scenarios, in the case of the first implementation, it ispossible to avoid or expect not to change the HARQ-ACK codebookconfiguration even though the BWP is changed.

Implementation 2

When a plurality of BWPs are set, the UE determines whether HARQ-ACKbits are generated based on a combination of downlink association setsor PDCCH monitoring occasions for all the set BWPs for each cell.Specifically, when a semi-static HARQ-ACK codebook is used, HARQ-ACKbits can be generated for each PDCCH monitoring occasion for all theBWPs set or for each PDCCH monitoring occasion in the union of downlinkassociation sets. In this case, the number of HARQ-ACK bits may be onebit or two bits, depending on the number of TBs.

On the other hand, when the dynamic HARQ-ACK codebook is used, HARQ-ACKbits can be generated according to scheduling of the PDSCH based on thecombination of the PDCCH monitoring occasions or the downlinkassociation set for all the BWPs set.

In the second implementation, the number of HARQ-ACK bits can beincreased. In particular, in the semi-static HARQ-ACK codebook, thenumber of HARQ-ACK bits may be excessively large. However, even when theBWP is changed dynamically and the PDCCH monitoring occasion, thePDCCH-to-PDSCH timing, and/or the PDSCH-to-HARQ-ACK feedback timing setare changed dynamically, the HARQ-ACK configuration does not change.

Implementation 3

The UE may generate HARQ-ACK bits based on the active BWP, i.e., active(downlink) BWP, at the corresponding HARQ-ACK feedback transmission timepoint. Alternatively, HARQ-ACK bits may be generated based on the(downlink) BWP corresponding to the PDSCH closest to the viewpoint amongthe PDSCHs associated with the HARQ-ACK feedback.

Specifically, in the case of a single cell based, the HARQ-ACK for thePDSCH that is being scheduled in the previous BWP can be dropped withoutbeing transmitted. In other words, when the UE configures the HARQ-ACKafter the BWP is changed, the HARQ-ACK bit for the PDCSH scheduled inthe BWP after the change is included in the HARQ-ACK configuration, andthe HARQ-ACK for the PDSCH scheduled in the previous BWP-ACK bits can betransmitted without being included in the HARQ-ACK configuration.

On the other hand, in the CA situation, the order between HARQ-ACK bitsfor a plurality of serving cells may be rearranged, so that encoding forHARQ-ACK feedback may need to be performed again.

However, such a problem can be avoided by setting the interval in whichthe BWP is changed to be long enough and not performing new (downlink)scheduling within the interval. Or, it can be expected that the HARQ-ACKfeedback for scheduling (downlink) occurring in the interval between BWPswitching, that is, in the BWP switching is all scheduled to correspondto the BWP before the change or correspond to the BWP after the change.

In the case of the third implementation, HARQ-ACK feedback detectionperformance can be improved by generating as many HARQ-ACK bits asnecessary. In particular, in the case of the semi-static HARQ-ACKcodebook, it is possible to generate as many HARQ-ACK bits as necessary.

Specifically, in the case of semi-static HARQ-ACK codebook, ingenerating the HARQ-ACK bit number, the HARQ-ACK bit associated with thePDCCH monitoring occasions for the BWP before the change is notgenerated, only HARQ-ACK bits associated with the PDCCH monitoringoccasions can be generated. That is, the number of HARQ-ACK bits is anumber of candidate PDSCH opportunities that can expect reception of thePDSCH in a plurality of slots according to the PDSCH-to-HARQ feedbacktiming related to the HARQ-ACK feedback, and generate HARQ-ACK bits asmany as the number of candidate PDSCH opportunities associated with thechanged BWP.

In other words, the number of HARQ-ACK bits after BWP switching isperformed may be less than the number of HARQ-ACK bits when BWPswitching is not performed. However, after a certain period of timesince the BWP switching is performed, all candidate PDSCH opportunitiesrelated to the HARQ-ACK feedback may be present in the slots after theBWP change. As time passes after the BWP change, the number of ACK bitsmay gradually increase. In other words, bits for candidate PDSCHopportunities associated with the pre-change BWP that are dropped on theHARQ-ACK bits are not included.

Implementation 4

When the UE determines that all the downlink BWPs indicated by the PDCCHscheduling PDSCH in the downlink association set corresponding to theHARQ-ACK feedback are all the same or when the PDCCH monitoring occasionset or HARQ-ACK feedback is used, the UE determines that the downlinkassociation set is the same.

For example, the downlink association set for HARQ-ACK feedback at onepoint may correspond to only one specific BWP for each cell. DifferentHARQ-ACK feedback may be performed in different Orthogonal Cover Code(OCC) and frequency/symbol regions when HARQ-ACK feedback is dividedinto ACK/NACK resource indicator (ART). For each different HARQ-ACKfeedback, the BWPs associated with the downlink association set may beindividually set.

In this case, a fallback operation may be implemented within the BWPswitching period. For example, in some implementations (e.g., in an NRsystem), the UE receives only one fallback DCI such as DCI format 1_0,and when the DAI value of the received fallback DCI is 1, it cantransmit only HARQ-ACK bits for the corresponding DCI.

In some implementations, the fallback DCI may be transmitted in a commonsearch space. In addition, when the UE detects PDCCH and/or PDSCH in thefirst slot or first PDCCH monitoring occasions in the downlinkassociation set associated with HARQ-ACK in the NR system, the UE maytransmit only HARQ-ACK bits for the corresponding PDSCH.

Alternatively, the BWP switching may be directed to the non-fallbackDCI, so that if the UE detects only one DCI with DAI=1, then regardlessof the DCI format, it may only transmit HARQ-ACK bits for that PDSCH. Inthis case, the DCI with DAI=1 may be a DCI scheduling the correspondingPDSCH. Specifically, even if only one DCI with DAI=1 is transmitted inSCell, i.e., DCI with DAI=1 is not transmitted in another cell, theHARQ-ACK bits for the corresponding PDSCH can be transmitted.

However, in case of using the semi-static HARQ-ACK codebook, there maybe no DAI field for the non-fallback DCI, and thus the PDSCH isscheduled in the first PDCCH monitoring occasion corresponding to thedownlink association set for HARQ—Only when the PDCCH is detected, theHARQ-ACK bit for the PDSCH can be transmitted. That is, even if thesemi-static HARQ-ACK codebook is set, HARQ-ACK bits for all PDCCHmonitoring occasions associated with the HARQ-ACK feedback are notgenerated but HARQ-ACK bits related to the DCI-based fallback operationwith DAI=Can be generated. At this time, during the BWP switchingperiod, the UE can utilize the DCI-based fallback operation with DAI=1.

In some implementations, the HARQ-ACK codebook generation methodaccording to the BWP change may be different depending on whether theHARQ-ACK codebook set in the above implementation is a semi-staticHARQ-ACK codebook or a dynamic HARQ-ACK codebook. In addition,implementations of the present disclosure do not necessarily have to beperformed singly, but may be performed in combination of theimplementations. That is, a plurality of methods included in the aboveimplementations may be used in combination. For example, in animplementation of the present disclosure, a fallback operation mayalways be supported.

Also, the downlink association set for the HARQ-ACK may be distinguishedaccording to the BWP index and/or ARI combination indicated by the DCI.For example, if some of the different BWP inter-PDCCH monitoringopportunities overlap, then based on the BWP index and/or ARI value inthe DCI transmitted in the overlapping region, the UE can determinewhich BWP based on the downlink association set to be referred to whengenerating the HARQ-ACK codebook. That is, if some of the PDCCHmonitoring opportunities between different BWPs overlap, then PDCCHscorresponding to PDSCHs in a downlink association set of a specific BWPcriterion may have the same BWP index and/or ARI. Specifically, the ARIvalue may be classified according to whether the ARI field value is thesame or not.

In addition, when the PUCCH resource set to be indicated by the ARI isdifferent for each BWP, the HARQ-ACK codebook generation andtransmission operation may be performed based on whether the finallyselected PUCCH resource is the same.

If the BWP indexes are different and the ARIs are the same, it may beconsidered that HARQ-ACKs for PDSCHs corresponding to different BWPs aretransmitted on the same channel. Specifically, HARQ-ACKs for PDSCHscorresponding to different BWPs can be simultaneously transmitted afterHARQ-ACKs are generated for each BWP, and are concurrently transmitted.In order to more efficiently reduce the payload size, HARQ-ACK may begenerated by union with respect to the downlink association set for BWP.

In some implementations of the present disclosure, the semi-staticHARQ-ACK codebook or the dynamic HARQ-ACK codebook may be UE-specificregardless of BWP, and when the codebook type is set for each BWP, allof them may have the same setting.

In some implementations (e.g., systems compatible with NR), the HARQ-ACKcodebook configuration method may be changed through higher layersignaling. In such scenarios, a need may arise to operate withoutambiguity between the UE and the gNB during the RRC reset period. Inthis case, potential ambiguity between the gNB and the UE may bemitigated by operating in the fallback operation mode described in theabove implementations within the period.

In the HARQ-ACK codebook type, whether a semi-static HARQ-ACK codebookor a dynamic HARQ-ACK codebook is configured may be changed according tothe downlink BWP and/or the uplink BWP. For example, a semi-staticHARQ-ACK codebook may be useful when the downlink association set sizefor HARQ-ACK feedback differs according to the downlink BWP, andconversely, a dynamic HARQ-ACK codebook may be useful.

For example, if the DL association set is large, the size of theHARQ-ACK codebook may be large, so it may be configured as a dynamicHARQ-ACK codebook.

On the other hand, when ambiguity may occur if a DAI-based dynamicHARQ-ACK codebook is used due to a change in channel quality orinterference environment according to the downlink BWP, then asemi-static HARQ-ACK codebook may be utilized. In this case, as the UEchanges the BWP dynamically, the HARQ-ACK codebook type may also bechanged dynamically.

Since the PUCCH will be transmitted in the PCcell (including the PSCellor the PUCCH-SCell), the HARQ-ACK codebook type may be determinedaccording to the PCell (downlink) BWP. For example, the presence of theDAI field in the DCI at SCell may be determined based on whether theHARQ-ACK codebook configured in the BWP of PCell is a dynamic HARQ-ACKcodebook. However, even in this case, the fallback DCI may still have acounter DAI field.

On the other hand, a DAI field may be created or excluded based on thetime point at which the BWP is actually changed. The UE assumes that thedownlink BWP indicated by the PDCCH in the DL association setcorresponding to the corresponding HARQ-ACK feedback is the same at thetime of HARQ-ACK feedback. For example, all of the DCIs associated withHARQ-ACK feedback may be regarded as assuming a semi-static HARQ-ACKcodebook or a dynamic HARQ-ACK codebook. Specifically, the HARQ-ACKfeedback may be divided into the BWP index and/or the ARI value in theassociated DCI, and the DCIs corresponding to the same HARQ-ACK feedbackchannel or the same HARQ-ACK feedback channel group may have a BWP indexand/or ARI value of the same value.

On the other hand, when the interval or BWP is changed such as when thesearch space configuration is changed, a fallback operation may beperformed. Here, the fallback operation refers to an operation based onthe DCI having DAI=1 or an operation of detecting the DCI only at thefirst PDCCH monitoring occasion of the downlink association set of theconfigured cell.

On the other hand, due to DCI-based BWP switching, there may be adiscrepancy between the required DCI field size and the actuallytransmitted DCI field size in the changed BWP.

For example, as can be seen in the example of FIG. 18, the DCI isreceived in the pre-change BWP, and the BWP is subsequently changedaccording to the received DCI indication. Then, if the DCI schedules thePDSCH in the (post-change) BWP after the change, then inconsistenciesmay occur between the number of required DCI bits depending on thesettings for the BWP before the change and the number of DCI bitsrequired depending on the settings for the BWP after the change. Thatis, the size of the bits required for the PDSCH scheduling transmittedin the BWP after the change may differ from the size of the bits of theDCI transmitted in the BWP before the actual change.

In this case, the bit field for the relevant setting contained in theDCI field may be zero padded or truncated prior to interpreting theinformation contained in the DCI, depending on the relevant settingwhere inconsistencies may occur. That is, when the UE interprets theDCI, it can interpret the DCI assuming that the bit field for therelevant setting is zero padded or truncated.

If the bit field size necessary for the changed BWP is smaller than orequal to the bit field size of the actually transmitted DCI, then theDCI may represent all possible values of the corresponding bit field, sothat the scheduling restriction due to the difference in field size doesnot occur. However, if the bit field size required for the changed BWPis greater than the bit field size of the actually transmitted DCI, thenthe DCI cannot point to some value of the bit field needed for thechanged BWP and thus may limit PDSCH scheduling.

Therefore, according to some implementations of the present disclosure,DCI analysis techniques of the UE will be described, which may addressmismatches that occur between the size of the DCI required forscheduling the PDSCH due to the BWP change and the size of the actuallytransmitted DCI.

Before explaining the analysis techniques for each DCI format, theoperation in terms of UE, base station and network according to theimplementation of the present disclosure will be described withreference to FIGS. 19 to 21, below.

FIG. 19 shows an example of an operation procedure according to thepresent disclosure from a UE perspective. Referring to the example ofFIG. 19, the UE receives (S1901) a DCI including first information forchanging an active BWP from a first BWP to a second BWP, and transmitsthe DCI included in the DCI based on the configurations for the secondBWP PDSCH scheduling related information (S1903). In someimplementations, the bits included in the DCI may be generated based onthe configuration for the first BWP. To interpret the schedulinginformation for the PDSCH received in the second BWP, bits based onsettings for the second BWP may be needed. If there is a discrepancybetween the number of bits required to interpret the PDSCH schedulinginformation and the number of bits included in the received DCI, then inaccordance with embodiments described below, the UE may interpret thereceived DCI and obtain scheduling information for the PDSCH.

If the UE obtains the PDSCH scheduling information through the receivedDCI analysis according to the implementations described further below,the PDSCH may be received in the second BWP based on the obtained PDSCHscheduling information (S1905).

FIG. 20 is a diagram showing an example of an operation procedure of abase station according to an implementation of the present disclosure.Referring to FIG. 20, the BS may transmit, to a UE, a DCI including thefirst information for changing the active BWP from the first BWP to thesecond BWP (S2001). In some implementations, in addition to the changeof the active BWP, the DCI may also include various information forscheduling the PDSCH. Although the PDSCH may be scheduled to betransmitted in the second BWP, the criterion of DCI generation may bethe configuration for the first BWP. For example, the DCI bit size maybe determined based on the configuration for the first BWP, and may beinconsistent with the bit size required for the UE in order to actuallyschedule the PDSCH transmitted from the second BWP.

Therefore, according to some implementations disclosed herein,techniques are disclosed for handling each bit field in view of suchinconsistency. However, if the bit size necessary for the second BWP islarger than the bit size of the actually transmitted DCI, then the BSmay schedule the PDSCH in the second BWP considering this. For example,the base station may consider the ambiguity of the size of the DCI thatcan occur due to the inconsistency between the setting for the first BWPand the setting for the second BWP, and may schedule the PDSCH in thesecond BWP within a range that can be represented by the bit size of theactually transmitted DCI. The BS may transmit the PDSCH in the secondBWP based on the DCI (S2003).

Referring to the example of FIG. 21, a base station may transmit, to aUE, a DCI including first information for changing an active BWP from afirst BWP to a second BWP (S2101). In some implementations, the DCI mayinclude various information for scheduling the PDSCH, in addition to thefirst information for changing the active BWP. In this case, althoughPDSCH may be scheduled to be transmitted in the second BWP, the criteriafor DCI generation may be based on the configuration for the first BWP.For example, the DCI bit size may be determined based on theconfiguration for the first BWP, and may be inconsistent with the bitsize required for the UE in order to actually schedule the PDSCHtransmitted from the second BWP.

Therefore, according to some implementations disclosed herein,techniques are disclosed for handling each bit field in view of suchinconsistency. However, if the bit size necessary for the second BWP islarger than the bit size of the actually transmitted DCI, then the BSmay schedule the PDSCH in the second BWP considering this. For example,the base station may consider the ambiguity of the size of the DCI thatcan occur due to the inconsistency between the setting for the first BWPand the setting for the second BWP, and may schedule the PDSCH in thesecond BWP within a range that can be represented by the bit size of theactually transmitted DCI.

In some implementations, the UE receiving the DCI analyzes and acquiresPDSCH scheduling related information included in the DCI based on theconfiguration for the second BWP (S2103). In some implementations, thebits included in the DCI may be generated based on the configuration forthe first BWP. To interpret the scheduling information for the PDSCHreceived in the second BWP, bits based on configurations for the secondBWP may be needed. If there is a discrepancy between the number of bitsrequired to interpret the PDSCH scheduling information and the number ofbits included in the received DCI, then in accordance with embodimentsdescribed below, the UE may interpret the received DCI and obtainscheduling information for the PDSCH.

In some implementations, the BS may transmit the PDSCH in the second BWPbased on the DCI (S2105).

Now, a description will be provided of an example of techniquesaddressing scenarios where a mismatch occurs between the DCI bit sizerequired for the changed BWP and the actually transmitted DCI bit sizefor each DCI format for scheduling the PDSCH.

Table 4 shows an example of fields of DCI format 0_1 that arezero-padded or truncated before analyzing the DCI, due to the BWPswitching.

TABLE 4 Related DCI field Related parameter configuration Possiblevalues Frequency resourceAllocation PUSCH-Config ENUMERATED domain{resourceAllocationType0, resource resourceAllocationType1, assignmentdynamicSwitch} rbg-Size PUSCH-Config ENUMERATED {config2}frequencyHoppingOffsetLists PUSCH-Config SEQUENCE (SIZE (1..4)) OFINTEGER (1 . . . maxNrofPhysicalResourceBlocks −1) locationAndBandwidthBWP provided INTEGER (0..37949) in BWP- UplinkCommon Timepusch-AllocationList PUSCH-Config SEQUENCE (SIZE domain(1..maxNrofUL-Allocations)) OF resource PUSCH- assignmentTimeDomainResourceAllocation Frequency resourceAllocation PUSCH-ConfigENUMERATED hopping {resourceAllocationType0, flagresourceAllocationType1, dynamicSwitch} SRS srs-ResourceIdList SRS-SEQUENCE (SIZE resource ResourceSet (1..maxNrofSRS- indicatorResourcesPerSet)) OF SRS- ResourceId Usage SRS- ENUMERATED ResourceSet{beamManagement, codebook, nonCodebook, antennaSwitching} maxRankPUSCH-Config INTEGER (1..4) txConfig PUSCH-Config ENUMERATED {codebook,nonCodebook} Precoding txConfig PUSCH-Config ENUMERATED {codebook,information nonCodebook} and number transformPrecoder PUSCH-ConfigENUMERATED {enabled, of layers disabled} maxRank PUSCH-Config INTEGER(1..4) codebookSubset PUSCH-Config ENUMERATED{fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent}Antenna transformPrecoder PUSCH-Config ENUMERATED {enabled, portsdisabled} txConfig PUSCH-Config ENUMERATED {codebook, nonCodebook}maxRank PUSCH-Config INTEGER (1..4) dmrs-Type DMRS- ENUMERATED {type2}UplinkConfig provided in PUSCH-Config maxLength DMRS- ENUMERATED {len2}UplinkConfig provided in PUSCH-Config PTRS- transformPrecoderPUSCH-Config ENUMERATED {enabled, DMRS disabled} association maxRankPUSCH-Config INTEGER (1..4) phaseTrackingRS DMRS- SetupRelease{PTRS-UplinkConfig} UplinkConfig provided in PUSCH-Config beta_offsetbetaOffsets UCI- CHOICE {dynamic indicator OnPUSCH SEQUENCE (SIZE (4))provided in OF BetaOffsets, PUSCH-Config semiStatic BetaOffsets} DMRStransformPrecoder PUSCH-Config ENUMERATED {enabled, sequence disabled}initialization

Referring to Table 4, when analyzing the DCI field included in the DCIformat 0_1 according to the BWP change, when performing zero padding ona bit field for frequency/time domain resource allocation, thescheduling flexibility may be limited However, the complexity of thesystem can be reduced. Also, when performing frequency hopping, zeropadding may correspond to non-frequency hopping being used for PUSCHtransmission. On the other hand, since the Sounding Reference Signal(SRS) is transmitted after the active UL (Uplink) BWP is changed, thegNB schedules DCI format 0_1 indicating UL BWP change without accurateinformation on the channel state or beam information for the new BWP do.In addition, when the BWP change is triggered, the TransmissionConfiguration Indication (TCI), Modulation and Coding Scheme (MCS)and/or Scheduling Request Indicator (SRI) due to BWP change cannot beused because the fallback DCI (e.g. DCI format 0_0) Indicator) may notbe accurate. On the other hand, the information about the new BWP may beinaccurate without regard to the number of bits available for each DCIfield.

Similarly, in an antenna port or PTRS-DMRS association, since the gNBcannot accurately determine the most suitable DMRS port to transmitPUSCH or PTRS before SRS reception, the bit field size associated withantenna port or PTRS-DMRS is not limited. In other words, the new BWPrelated antenna port or the PTRS-DMRS association information may beinaccurate regardless of the bit field size limitation because the basestation cannot accurately grasp the antenna port or PTRS-DMRSassociation information for the BWP after the change.

In scenarios where the beta offset indicator is conservatively set asthe semi-static beta offset, a dynamic beta offset indicator can beused. On the other hand, one of the values that can be indicated by thebeta offset indicator may need to be conservatively set. For example,the conservatively set value may be indicated using a bit field index 0.

The DMRS sequence initialization can be used to support MU-MIMO (MultiUser-Multi Input Multi Output). Even if the DCI format 0_1 indicatingthe UL BWP change does not have a bit field for initializing the DMRSsequence or the value of the DMRS sequence initialization is set to 0,the gNB may set the DMRS sequence of 1 to support other UEs for MU—TheDCI indicating the initialization can be scheduled.

To summarize the above description, no restriction is placed on theselection of the bit field of the DCI format 0_1 even if a large part ofthe bit fields for BWP is truncated after the change. As such, even whenthe BWP is changed, the bit fields of the DCI format 0_1 can be used asthey are. However, irrespective of the size of the bit field,information regarding some DCI fields, such as SRS resource indication,precoding information, number of layers, antenna port and/or PTRS-DMRSassociation information, may not be accurate.

The following [Table 5] shows an example of fields of the DCI format 1_1that are zero-padded or truncated before analyzing the DCI, due to theBWP change.

TABLE 5 Related DCI field Related parameter configuration Possiblevalues Frequency resourceAllocation PDSCH-Config ENUMERATED domain{resourceAllocationType0, resource resourceAllocationType1, assignmentdynamicSwitch} rbg-Size PDSCH-Config ENUMERATED {config1, config2}locationAndBandwidth BWP provided INTEGER (0..37949) in BWP-DownlinkCommon Time pusch-AllocationList PDSCH-Config SEQUENCE (SIZEdomain (1..maxNrofUL- resource Allocations)) OF PDSCH- assignmentTimeDomainResourceAllocation VRB-to- resourceAllocation PDSCH-ConfigENUMERATED PRB {resourceAllocationType0, mappingresourceAllocationType1, dynamicSwitch} PRB prb-BundlingTypePDSCH-Config CHOICE { bundling static SEQUENCE size {bundleSizeindicator ENUMERATED {n4, wideband} }, dynamic SEQUENCE {bundleSizeSet1ENUMERATED {n4, wideband, n2-wideband, n4-wideband} bundleSize5Set2ENUMERATED {n4, wideband}} Rate rateMatchPatternToAddModListPDSCH-Config SEQUENCE (SIZE matching (1..maxNrofRateMatchPatterns))indicator OF RateMatchPattern ZP CSI-RS zp-CSI-RS- PDSCH-Config SEQUENCE(SIZE trigger ResourceToAddModList (1..maxNrofZP-CSI-RS- Resources)) OFZP-CSI-RS- Resource For maxNrofCodeWordsScheduled PDSCH-ConfigENUMERATED {n1, n2} transport ByDCI block 2 Antenna dmrs-Type DMRS-ENUMERATED {type2} port (s) DownlinkConfig provided in PDSCH-ConfigmaxLength DMRS- ENUMERATED {len2} DownlinkConfig provided inPDSCH-Config Transmission tci-PresentInDCI ControlResource {enabled}configuration Set provided in ENUMERATED indication PDCCH-Config DMRSscramblingID1 DMRS- INTEGER (0..65535) sequence DownlinkConfiginitialization provided in PDSCH-Config

When performing zero padding on the bit field for frequency/time domainresource allocation, the scheduling flexibility may be limited, but thecomplexity of the system may be reduced. If the VRB-to-PRB mapping fieldis zero padded, then non-interleaved VRB-to-PRB mapping may be used forPDSCH transmission.

If the PRB bundling size indicator is zero padded, then a value ofsecond PRB bundling size may be used for PDSCH reception. In somescenarios, even this may not be disadvantageous in terms of schedulingflexibility compared to semi-static PRB bundling size.

The rate matching indicator or the ZP CSI-RS trigger may be meaningfulonly if the rate matching pattern or the ZP CSI-RS pattern to beindicated (by the rate matching indicator or by the ZP CSI-RS Trigger)overlaps (partially or completely) with the assigned resources that areindicated by the time/frequency domain resource allocation. Therefore,even if there is a restriction on the bit field size of the ratematching indicator or the ZP CSI-RS trigger, the gNB can control so asto prevent overlapping of the allocated resources with the rate matchingpattern or the ZP CSI-RS pattern that cannot be indicated by therate-matching indicator or the ZP CSI-RS trigger, respectively. As such,constraining the bit field size of the rate matching indicator or the ZPCSI-RS trigger is not problematic for UE and base station operation.

In the bit field for transport block 2, if the DCI format 1_1 indicatingactive DL BWP change can schedule only one transport block, but the newBWP (i.e., the changed BWP) supports up to two transport blocks, then insome implementations, the second transmission block may be disabled. Inother words, according to some implementations, if a pre-change BWP inwhich DCI format 1_1 indicating an active DL BWP change supports onlyone transport block, but the new BWP supports up to two transportblocks, then the second transport block may be disabled. Therefore, inthis case, a condition may be implemented for disabling a transportblock, during determination of the transport block size.

As a specific example, even if the parameter‘maxNrofCodeWordsScheduledByDCI’ configured by upper layers indicatesthat two codewords transmissions are enabled, if the DCI indicating theactive BWP change contains only one set of MCS, NDI, and RV bitfields,then only one transport block may be enabled. For example, even if‘maxNrofCodeWordsScheduledByDCI’ is set to 2 for the BWP after thechange by the upper layer, if there is only one set of MCS, NDI, and RVbitfields in the DCI that indicates the change of the active BWP sent inthe BWP before the change, then the second transport block may bedisabled.

Here, if the second transport block is disabled, then according to someimplementations, the UE may detect the DCI assuming that the MCS, NDI,and RV bit field sets for the second transport block in the DCI format1_1 are transmitted with zero padding. Alternatively, the UE may ignorethe MCS, NDI, and RV bit field sets for the second transport block inDCI format 1_1. In some implementations, the UE may perform bothactions. That is, the UE can ignore the field set assuming that the MCS,NDI, and RV bit field sets for the second transport block in the DCIformat 1_1 are zero padded.

In some implementations, the DMRS sequence initialization may be used tosupport MU-MIMO. For example, even in scenarios where the DCI format 1_1(indicating DL BWP switching) does not have a bitfield for initializingthe DMRS sequence (and thus the value for initializing the DMRS sequenceis set to 0), the gNB may nonetheless schedule DCI indicating DMRSsequence initialization of 1 for another UE to support the MU-MIMOoperation.

In other words, for some DCI fields (e.g., Antenna Ports, orTransmission Configuration Indication (TCI)), regardless of the size ofthe bitfield, the network may not know the information for the fieldcorresponding to the BWP after switching. Consequently, even if abitfield is truncated significantly to match the new BWP afterswitching, there is no restriction on the bitfield selection for the DCIformat 1_1.

For MIMO-related parameters, since the CSI-RS or SRS will be transmittedafter the BWP switching, the gNB may not be able to perform channelestimation or beam detection on the new BWP (i.e., BWP after switching)to schedule the PDSCH or PUSCH. In this case, rather than use aDCI-indicated Transmitted Precoding Matrix Indicator (TPMI), antennaports, Scheduling Request Indicator (SRI), or Transmission ConfigurationIndicator (TCI), instead, a default setting may be used, as in initialtransmission before RRC (Radio Resource Control) configuration.

As a specific example, if the PUSCH is scheduled by DCI which indicatesactive UL BWP switching, then the beam information for the PUSCHtransmission may re-use the same beam information as the beaminformation of the PUCCH resource having a lowest index among PUCCHresources. Furthermore, if the PDSCH is scheduled by DCI which indicatesan active DL BWP switching, then the beam information for the PDSCHtransmission may re-use the same beam information as the beaminformation of the Control Resource Set (CORESET) having a lowest indexamong CORESETs.

In some implementations, such operations may ignore DCI fields that arenot present in the fallback DCI format, such that operations behaveanalogously to those of PDSCH/PUSCH scheduling that is scheduled byfallback DCI. In other words, if a default setting is assumed, it may beconsidered to ignore DCI fields that do not exist in the fallback DCIformat, in order to simplify the DCI directing the BWP change.

For example, consider a scenario where DCI schedules a PDSCHtransmission in a post-switching BWP, and where that DCI indicates theBWP switching. In such scenarios, Quasi Co-Location (QCL) information,spatial relation information, or Transmission Configuration Indication(TCI) information may be assumed to be the same as the CORESET of thelowest index.

For example, after a change in BWP by DCI indicating the BWP switching,the QCL information, spatial relationship information, or TCIinformation for the PDSCH transmission scheduled in the BWP may be thesame as the QCL information, the spatial relationship information, orthe TCI information that is configured for the CORESET associated withthe DCI indicating the BWP change. Alternatively, it may be assumed thatthe new BWP (i.e., BWP after switching) is equal to QCL information,spatial relationship information, or TCI information for the PDSCH thatis scheduled by the fallback DCI.

Similarly, in PUSCH transmission that is scheduled by DCI indicating theBWP switching, it may be assumed that QCL information, spatialrelationship information, or SRS resource indicator information is thesame as the PUCCH of the lowest index, or that it is the same as QCLinformation, spatial relationship information, or SRS resource indicatorinformation for a Msg3 in the new BWP (post-switching). Specifically,the above-described techniques may be applied collectively to the DCIfor changing the BWP.

In some implementations, the DCI-based BWP change may occur flexibly,and in some cases, operations based on the default setting may beperformed only for a specific combination of MIMO-related parameters, inorder to use the DCI indication-based MIMO parameter value. For example,when the MIMO-related parameters are all set to 0, the operationaccording to the default setting can be performed.

FIG. 22 shows an example of a radio communication apparatus according toan implementation of the present disclosure.

The wireless communication apparatus illustrated in FIG. 22 mayrepresent a terminal and/or a base station according to animplementation of the present disclosure. However, the wirelesscommunication apparatus of FIG. 22 is not necessarily limited to theterminal and/or the base station according to the present disclosure,and may implement various types of apparatuses, such as a vehiclecommunication system or apparatus, a wearable apparatus, a laptop, etc.

In the example of FIG. 22, a terminal and/or a base station according toan implementation of the present disclosure includes at least oneprocessor 10 such as a digital signal processor or a microprocessor, atransceiver 35, a power management module 5, an antenna 40, a battery55, a display 15, a keypad 20, at least one memory 30, a subscriberidentity module (SIM) card 25, a speaker 45, and a microphone 50, andthe like. In addition, the terminal and/or the base station may includea single antenna or multiple antennas. The transceiver 35 may be alsoreferred to as an RF module.

The at least one processor 10 may be configured to implement thefunctions, procedures and/or methods described in FIGS. 1 to 21. In atleast some of the implementations described in FIGS. 1 to 21, the atleast one processor 10 may implement one or more protocols, such aslayers of the air interface protocol (e.g., functional layers).

The at least one memory 30 is connected to the at least one processor 10and stores information related to the operation of the at least oneprocessor 10. The at least one memory 30 may be internal or external tothe at least one processor 10 and may be coupled to the at least oneprocessor 10 via a variety of techniques, such as wired or wirelesscommunication.

The user can input various types of information (for example,instruction information such as a telephone number) by varioustechniques such as pressing a button on the keypad 20 or activating avoice using the microphone 50. The at least one processor 10 performsappropriate functions such as receiving and/or processing information ofthe user and dialing a telephone number.

It is also possible to retrieve data (e.g., operational data) from theSIM card 25 or the at least one memory 30 to perform the appropriatefunctions. In addition, the at least one processor 10 may receive andprocess GPS information from the GPS chip to obtain location informationof the terminal and/or base station such as vehicle navigation, mapservice, or the like, or perform functions related to locationinformation. In addition, the at least one processor 10 may displaythese various types of information and data on the display 15 forreference and convenience of the user.

The transceiver 35 is coupled to the at least one processor 10 totransmit and/or receive radio signals, such as RF signals. At this time,the at least one processor 10 may control the transceiver 35 to initiatecommunications and transmit wireless signals including various types ofinformation or data, such as voice communication data. The transceiver35 may comprise a receiver for receiving the radio signal and atransmitter for transmitting. The antenna 40 facilitates thetransmission and reception of radio signals. In some implementations,upon receipt of a radio signal, the transceiver 35 may forward andconvert the signal to a baseband frequency for processing by the atleast one processor 10. The processed signals may be processed accordingto various techniques, such as being converted into audible or readableinformation, and such signals may be output via the speaker 45.

In some implementations, a sensor may also be coupled to the at leastone processor 10. The sensor may include one or more sensing devicesconfigured to detect various types of information, including velocity,acceleration, light, vibration, and the like. The at least one processor10 receives and processes the sensor information obtained from thesensor such as proximity, position, image, and the like, therebyperforming various functions such as collision avoidance and autonomoustravel.

Meanwhile, various components such as a camera, a USB port, and the likemay be further included in the terminal and/or the base station. Forexample, a camera may be further connected to the at least one processor10, which may be used for a variety of services such as autonomousnavigation, vehicle safety services, and the like.

FIG. 22 merely illustrates one example of an apparatuses constitutingthe terminal and/or the base station, and the present disclosure is notlimited thereto. For example, some components, such as keypad 20, GlobalPositioning System (GPS) chip, sensor, speaker 45 and/or microphone 50may be excluded for terminal and/or base station implementations in someimplementations.

Specifically, in order to implement implementations of the presentdisclosure, an example of operations of the wireless communicationapparatus represented in FIG. 22 in the case of a terminal according toan implementation of the present disclosure will be described. If thewireless communication device is a terminal according to animplementation of the present disclosure, the at least one processor 10may include a transceiver 35 to receive a DCI containing firstinformation for changing an active BWP from a first BWP to a second BWP,and may interpret and obtain PDSCH scheduling related informationincluded in the DCI based on the configuration for the second BWP. Thebits included in the DCI may be generated based on the configuration forthe first BWP, and bits based on configurations for the second BWP maybe needed to interpret the scheduling information for the PDSCH receivedat the second BWP. If there is a discrepancy between the number of bitsrequired to interpret the PDSCH scheduling information and the number ofbits included in the received DCI, then the DCI may be interpretedaccording to the implementations described based on FIGS. 1 to 21 and[Table 4] to [Table 5] to obtain the scheduling information for thePDSCH.

If the at least one processor 10 obtains PDSCH scheduling informationthrough a DCI interpretation in accordance with the implementationsdescribed based on FIGS. 1 to 21 and [Table 4] to [Table 5], then the atleast one processor 10 may control the transceiver 35 to receive thePDSCH in the second BWP based on the obtained PDSCH schedulinginformation.

In some implementations of the present disclosure, when the wirelesscommunication apparatus represented in FIG. 15 is a base station, the atleast one processor 10 may control the transceiver 35 to send the DCI tothe UE that includes the first information for changing the active BWPfrom the first BWP to the second BWP. In this case, the DCI may includevarious information for scheduling the PDSCH in addition to the changeof the active BWP. In this case, the PDSCH may be scheduled to betransmitted in the second BWP, for example. That is, the DCI bit sizemay be determined based on the setting for the first BWP, and may beinconsistent with the bit size required for the UE in order to actuallyschedule the PDSCH transmitted from the second BWP. In such scenarios,the interpretation of each bit field caused by such inconsistency may beperformed in accordance with implementations described based on FIGS. 1to 21 and [Table 4] to [Table 5].

However, if the bit size necessary for the second BWP is larger than thebit size of the actually transmitted DCI, then the BS may schedule thePDSCH in the second BWP considering this. For example, if the UE 10 hasa mismatch between the configurations for the first BWP and theconfigurations for the second BWP, given the ambiguity of the size ofthe DCI that can occur, then the PDSCH in the second BWP may bescheduled within a range that can be represented by the bit size of theactually transmitted DCI. Meanwhile, the base station may control thetransceiver 35 to transmit the PDSCH in the second BWP based on the DCI.

The implementations described above are those in which the elements andfeatures of the present disclosure are combined in a predetermined form.Each component or feature shall be considered optional unless otherwiseexpressly stated. Each component or feature may be implemented in a formthat is not combined with other components or features. It is alsopossible to construct implementations of the present disclosure bycombining some of the elements and/or features. The order of theoperations described in the implementations of the present disclosuremay be changed. Some configurations or features of certainimplementations may be included in other implementations, or may bereplaced with corresponding configurations or features of otherimplementations. It is clear that the claims that are not expresslycited in the claims may be combined to form an implementation or beincluded in a new claim by an amendment after the application.

The specific operation described herein as being performed by the basestation may be performed by its upper node, in some cases. That is, itis apparent that various operations performed for communication with aterminal in a network including a plurality of network nodes including abase station can be performed by the base station or by a network nodeother than the base station. A base station may be replaced by termssuch as a fixed station, a Node B, an eNode B (eNB), an access point,and the like.

Implementations according to the present disclosure may be implementedby various means, for example, hardware, firmware, software or acombination thereof. In the case of hardware implementation, animplementation of the present disclosure may include one or moreapplication specific integrated circuits (ASICs), digital signalprocessors (DSPs), digital signal processing devices (DSPDs),programmable logic devices (PLDs) field programmable gate arrays,processors, controllers, microcontrollers, microprocessors, and thelike.

In the case of an implementation by firmware or software, animplementation of the present disclosure may be implemented in the formof a module, a procedure, a function, or the like for performing thefunctions or operations described above. The software code can be storedin a memory unit and driven by the processor. The memory unit may belocated inside or outside the processor, and may exchange data with theprocessor by various well-known means.

It will be apparent to those skilled in the art that the presentdisclosure may be embodied in other specific forms without departingfrom the spirit of the disclosure. Accordingly, the above descriptionshould not be construed in a limiting sense in all respects and shouldbe considered illustrative. The scope of the present disclosure shouldbe determined by rational interpretation of the appended claims, and allchanges within the scope of equivalents of the present disclosure areincluded in the scope of the present disclosure.

Although the method and apparatus for transmitting and receiving thedownlink data channel have been described with reference to the fifthgeneration NewRAT system, the present disclosure can be applied tovarious wireless communication systems other than the fifth generationNewRAT system.

1. A method for receiving a Physical Downlink Shared Channel (PDSCH) bya user equipment (UE) in a wireless communication system, the UEcomprising: receiving, in a first Bandwidth Part (BWP), Downlink ControlInformation (DCI) including first information for switching an activeBWP from the first BWP to a second BWP and second information related toa Transport Block (TB) for the PDSCH; and receiving, in the second BWP,the PDSCH based on the first information and the second information,wherein, based on (i) the DCI scheduling only 1 TB and (ii) the secondBWP supporting 2 TBs, information related to a second TB among the 2 TBsis disabled.
 2. The method of claim 1, wherein the second informationincludes bits set for Modulation and Coding Scheme (MCS), New dataIndicator (NDI) and Redundancy Version (RV) for a first TB among the 2TBs.
 3. The method of claim 1, wherein the UE assumes that informationrelated to the second TB is zero-padded.
 4. The method of claim 1,wherein Transmission Configuration Indication (TCI) information of thesecond BWP is same with TCI information related to the DCI.
 5. Themethod of claim 4, wherein the TCI information related to the DCI is forControl Resource Set (CORESET) related to the DCI.
 6. An apparatus forreceiving a Physical Downlink Shared Channel (PDSCH) in a wirelesscommunication system, the apparatus comprising: at least one processor;and at least one memory operably connectable to the at least oneprocessor and storing instructions that, when executed by the at leastone processor, perform operations comprising: receiving, in a firstBandwidth Part (BWP), Downlink Control Information (DCI) including firstinformation for switching an active BWP from the first BWP to a secondBWP and second information related to a Transport Block (TB) for thePDSCH; and receiving, in the second BWP, the PDSCH based on the firstinformation and the second information, wherein, based on (i) the DCIscheduling only 1 TB and (ii) the second BWP supporting 2 TBs,information related to a second TB among the 2 TBs is disabled.
 7. Theapparatus of claim 6, wherein the second information includes bits setfor Modulation and Coding Scheme (MCS), New data Indicator (NDI) andRedundancy Version (RV) for a first TB among the 2 TBs.
 8. The apparatusof claim 6, wherein the UE assumes that information related to thesecond TB is zero-padded.
 9. The apparatus of claim 6, whereinTransmission Configuration Indication (TCI) information of the secondBWP is same with TCI information related to the DCI.
 10. The apparatusof claim 9, wherein the TCI information related to the DCI is forControl Resource Set (CORESET) related to the DCI.
 11. A user equipment(UE) for receiving a Physical Downlink Shared Channel (PDSCH) in awireless communication system, the UE comprising: at least onetransceiver; at least one processor; and at least one memory operablyconnectable to the at least one processor and storing instructions that,when executed by the at least one processor, perform operationscomprising: receiving, in a first Bandwidth Part (BWP), Downlink ControlInformation (DCI) including first information for switching an activeBWP from the first BWP to a second BWP and second information related toa Transport Block (TB) for the PDSCH; and receiving, in the second BWP,the PDSCH based on the first information and the second information,wherein, based on (i) the DCI scheduling only 1 TB and (ii) the secondBWP supporting 2 TBs, information related to a second TB among the 2 TBsis disabled.
 12. The UE of claim 11, wherein the second informationincludes bits set for Modulation and Coding Scheme (MCS), New dataIndicator (NDI) and Redundancy Version (RV) for a first TB among the 2TBs.
 13. The UE of claim 11, wherein the UE assumes that informationrelated to the second TB is zero-padded.
 14. The UE of claim 11, whereinTransmission Configuration Indication (TCI) information of the secondBWP is same with TCI information related to the DCI.
 15. The UE of claim14, wherein the TCI information related to the DCI is for ControlResource Set (CORESET) related to the DCI.